-
Notifications
You must be signed in to change notification settings - Fork 3.3k
{KeyVault} Support more long-running operations #14890
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
||
|
|
||
| def recover_keyvault(cmd, client, vault_name, resource_group_name, location): | ||
| def recover_keyvault(cmd, client, vault_name, resource_group_name, location, no_wait=False): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will this be a breaking change to user if no_wait default false?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will this be a breaking change to user if no_wait default false?
@yungezz No, it's not a breaking change. The previous behavior is synchronous as well.
|
Do they all have |
@qwordy Yes, all of these commands have
|
|
hi @fengzhou-msft could you pls help to review? thanks |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Support more long-running operations:
az keyvault recoveraz keyvault network-rule addaz keyvault network-rule removeaz keyvault set-policyaz keyvault delete-policyThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.